Skip to content

chore(main): release 0.2.0#10

Merged
GREENFONTS merged 1 commit into
mainfrom
release-please--branches--main
Jun 30, 2026
Merged

chore(main): release 0.2.0#10
GREENFONTS merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@GREENFONTS

Copy link
Copy Markdown
Collaborator

🤖 I have created a release beep boop

0.2.0 (2026-06-30)

Features

  • add card transactions and automated release tagging (25a62b3)
  • add card transactions client (charge, OTP, 3DS authorize) (73cc17e)

This PR was generated with Release Please. See documentation.

@GREENFONTS
GREENFONTS merged commit 17013f2 into main Jun 30, 2026
3 checks passed
GREENFONTS added a commit that referenced this pull request Jun 30, 2026
PR #10 merged 0.2.0's manifest/changelog bump, but no v0.2.0 tag ever
got created or pushed - skip-github-release turned out to skip the
underlying git tag as well, not just the GitHub Release object
(googleapis/release-please-action#1034). Since release.yml only
triggers on a tag push, this silently broke both the git release and
the actual NuGet publish for 0.2.0.

Replaced skip-github-release with draft: true instead: release-please
still creates the tag (restoring the trigger chain) plus a draft
(not publicly visible) GitHub Release. release.yml's publish job now
explicitly un-drafts that same release (draft: false) only after a
successful, approved NuGet push, rather than creating a second one -
softprops/action-gh-release updates an existing release for a tag
rather than failing or duplicating.
@GREENFONTS

Copy link
Copy Markdown
Collaborator Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant